-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ Initial scaffolding for operator #4117
✨ Initial scaffolding for operator #4117
Conversation
@wfernandes: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cc @fabriziopandini @CecileRobertMichon I know this PR looks enormous but it's just a few I'm trying to break out the work for the operator into smaller PRs with respective issues so that the work isn't too overwhelming. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wfernandes thanks!
I have added a couple of comments, mostly about changes required in order to make the default Kubebuilder scaffolding more consistent/integrated with the rest of the codebase.
Up to you if to tackle this comments within this PR or in follow up PRs.
Changes LGTM to me given the assumption this is plain "kubebuilder" scaffholding and #4126 is going to make everything more consistent/integrated with the rest of the codebase (thus addressing above comments). |
9404d34
to
94f2983
Compare
@fabriziopandini @CecileRobertMichon LMK if y'all think other changes are needed in this specific PR. Just FYI, I have #4126 and #4132 in the queue ready to be rebased and reviewed as well. So there may be suggestions or changes that have already been addressed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold |
94f2983
to
eae016e
Compare
I moved the code to |
docs/book/src/tasks/healthcheck.md
Outdated
@@ -16,15 +16,16 @@ at the bottom of this page for full details of MachineHealthCheck limitations. | |||
|
|||
## What is a MachineHealthCheck? | |||
|
|||
A MachineHealthCheck is a resource within the Cluster API which allows users to define conditions under which Machines within a Cluster should be considered unhealthy. | |||
A MachineHealthCheck is a resource within the Cluster API which allows users to define conditions under which Machines within a Cluster should be considered unhealthy. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those changes seems from a commit not relevant for this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, since the operator is in a separate branch, these commits come from a rebase. I can remove them from the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unnecessary commits removed, all should be fine now.
eae016e
to
606c913
Compare
As per #4117 (review) this PR introduces kubebuilder standard scaffolding, but there are changes to be applied in order to make things more consistent with the CAPI repository. I'm ok to get these point fixed in follow up PRs, but given that now more people are going to work on this I would like to get them tracked somewhere (one or more new issues, or a comment in existing ones). For your convenience below the list of things captured in the previous review:
|
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@fabriziopandini Thank you for your review and suggestions. Some of your points already might've been addressed in 2 other PRs related to the operator. I do agree this should all be tracked and fixed in follow-up PRs. |
606c913
to
ec84695
Compare
Domain is cluster.x-k8s.io Create API scaffolding for CoreProvider kubebuilder create api --group operator --version v1alpha4 --kind CoreProvider Create API scaffolding for BootstrapProvider kubebuilder create api --group operator --version v1alpha4 --kind BootstrapProvider Created Resources, not controllers Create API scaffolding for ControlPlaneProvider kubebuilder create api --group operator --version v1alpha4 --kind ControlPlaneProvider Created Resources, not controllers Create API scaffolding for InfrastructureProvider kubebuilder create api --group operator --version v1alpha4 --kind InfrastructureProvider Created Resources, not controllers Add placeholders for ProviderSpec and ProviderStatus Fix some module imports. Will be cleaned up in future PRs. Fix boilerplate on files Move operator to exp folder
ec84695
to
ced6551
Compare
@fabriziopandini CLA check now passes and commits are squashed. |
given that future work is tracked in #4246 |
@alexander-demichev this is still a draft PR, are you ready to move it to PR and remove the hold? |
it's not a draft PR anymore, should be ready for merging. |
I still see "draft" at the top under the title, and it still has WIP and hold labels. I don't see an option to publish the PR, maybe only @wfernandes can do it since he's the PR author. If not you might have to open a new PR from the same branch so we can merge it @alexander-demichev. |
/hold cancel |
@CecileRobertMichon the PR should now be ready for merging. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
This PR adds the initial bare bones scaffolding for the CAPI operator.
Other Notes
make
commands coming in a separate PR.Dockerfile
updates in a separate PR.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Ref #3833
Fixes #4118
/area api
/area operator